Method, device, client and server for interaction

ABSTRACT

An interaction method, device, client and server are provided. The method includes that: a client scans a target two-dimensional code (for example, a Quick Response code) to acquire a URL of the target two-dimensional code; the client sends the URL to an associated third-party server; the client receives multifunction information returned from the third-party server according to the URL, wherein each piece of the multifunction interaction information includes interaction type information; the client interacts with the third-party server according to the multifunction information. The present disclosure makes it possible that: during scanning a two-dimensional code, a client can directly interact with a third-party server, the interaction applications can simply be acquired via scanning, instead of pre-scanning and manually initiating an interaction with the scanned contents, such that the operations are simple and convenient.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a U.S. continuation application of InternationalApplication PCT/CN2014/072717, with an international filing date of Feb.28, 2014, claiming the priority benefit of Chinese Patent ApplicationNo. 201310211198.3 filed on May 30, 2013, the contents of which are bothincorporated by reference herein in their entireties for all purposes.

FIELD OF THE PRESENT DISCLOSURE

The present disclosure relates to the field of Internet technology, andin particular, to a method, device, client and server for interaction.

BACKGROUND

Two-dimensional code scanning, which refers to acquiring contents andinformation from a picture of two-dimensional code by a clientapplication of a mobile terminal, is typically used in areas of barcodesscanning, resources scanning and downloading, and train ticketsscanning, etc. As the grown of the two-dimensional code industry, andintellectualization trend of mobile terminals, applications of thetwo-dimensional code will be more and more popular. People may notice avariety of the two-dimensional code advertisements on billboards ofsubways or bus stations, for example, two-dimensional code basedshopping has been widely applied to outdoor advertising by 1^(st) Store,Taobao and Jingdong Mall. The two-dimensional code effectively increasesthe enjoyment and convenience of participating Marketing activities, sothat it attracts a plenty of consumers to join activities of brands, andthen an interactive relationship with the brands will be established.

Currently, a way to interact with merchants via two-dimensional codescanning may be: when a user of a mobile terminal requires to scan atwo-dimensional code advertisement, a local software for scanning thetwo-dimensional code on the mobile terminal will be activated to scanthe two-dimensional code and obtain contents of the two-dimensionalcode. If any further interaction operation is needed, the interactionoperation with the obtained contents will be started manually, whichbrings a lot of efforts and complexity to the operation process. Forexample, when the user wants to call a scanned number, the user stillneeds to dial the number manually after obtaining the number byscanning.

SUMMARY OF THE PRESENT INVENTION

The embodiments of the present disclosure provide an interaction method,which intends to solve problems that during scanning a two-dimensionalcode in prior art, the required interaction operations to the scannedcontents need to be operated manually, which brings a lot of efforts andcomplexity to the operation process.

The present embodiments provide the following technical solutions:

In one aspect of the present disclosure, an interaction method isprovided, comprising:

scanning, by a client, a target two-dimensional code to acquire a URL inthe target two-dimensional code;

sending, by the client, the URL to a third-party server;

receiving, by the client, multifunction interaction information that isreturned from the third-party server according to the URL, wherein eachpiece of the multifunction interaction information includes interactiontype information; and

interacting, by the client, with the third-party server based on themultifunction interaction information.

In another aspect of the present disclosure, an interaction method isprovided, comprising:

receiving, by a third-party server, a URL sent from a client;

sending, by the third-party server, multifunction interactioninformation to the client according to the URL, wherein each piece ofthe multifunction interaction information includes interaction typeinformation; and

interacting, by the third-party server, with the client based on themultifunction interaction information.

In another aspect of the present disclosure, an interaction device for aclient is provided, comprising:

a URL acquiring unit, configured to scan a target two-dimensional codeand acquire a URL from the target two-dimensional code;

a URL sending unit, configured to send the URL to an third-party server;

an information receiving unit, configured to receive multifunctioninteraction information returned from the third-party server accordingto the URL, wherein each piece of the multifunction interactioninformation includes interaction type information; and

an interaction unit, configured to interact with the third-party serverbased on the multifunction interaction information.

In another aspect of the present disclosure, a client is provided,comprising the above interaction device.

In the fifth aspect of the present disclosure, another interactiondevice for a third-party server is provided, comprising:

a URL receiving unit, configured to receive a URL sent from a client;

an information sending unit, configured to send multifunctioninteraction information to the client according to the URL, wherein eachpiece of the multifunction interaction information includes interactiontype information; and

an interaction unit, configured to interact with the client based on themultifunction interaction information.

In another aspect of the present disclosure, a third-party server isprovided, comprising the above interaction device.

Compared with prior art in the field, the advantage effect of thepresent disclosure is: a client scans the target two-dimensional code toacquire a URL of the target two-dimensional code; the client sends theURL to an associated third-party server; the client receivesmultifunction interaction information returned from the third-partyserver according to the URL, wherein each piece of the multifunctioninteraction information includes interaction type information; theclient interacts with the third-party server based on the multifunctioninteraction information. The present disclosure makes it possible that:during scanning a two-dimensional code, a client can directly interactwith a third-party server, the interaction applications can simply beacquired via scanning, instead of pre-scanning and manually initiatingan interaction with the scanned contents, such that the operations aresimple and convenient.

DESCRIPTION OF THE DRAWINGS

To better illustrate the technical solution of embodiments of thepresent disclosure, brief introductions to the drawings needed to beused in the description of embodiments will be made in the below. It isobvious that the drawings in the following description are but forexemplary embodiments of the present disclosure, and that a person ofordinary skilled in the art may derive additional draws based on thesefigures under the precondition that not paying creative efforts.

FIG. 1 is a flow chart that illustrates an implementation of aninteraction method provided by one embodiment of the present disclosure;

FIG. 2 is a flow chart that illustrates an implementation of aninteraction method provided by another embodiment of the presentdisclosure;

FIG. 3 is a flow chart that illustrates an interaction between a clientand a third-party server provided by another embodiment of the presentdisclosure;

FIG. 4 is a flow chart that illustrates an interaction method providedby another embodiment of the present disclosure;

FIG. 5 is a flow chart that illustrates an implementation of aninteraction method provided by another embodiment of the presentdisclosure;

FIG. 6 is a flow chart that illustrates an implementation of aninteraction method provided by another embodiment of the presentdisclosure;

FIG. 7 is a flow chart that illustrates an implementation of aninteraction method provided by another embodiment of the presentdisclosure;

FIG. 8 is a block diagram that illustrates an interaction deviceprovided by another embodiment of the present disclosure;

FIG. 9 is a block diagram that illustrates an interaction deviceprovided by another embodiment of the present disclosure;

FIG. 10 is a block diagram that illustrates an interaction deviceprovided by another embodiment of the present disclosure;

FIG. 11 is a block diagram that illustrates an interaction deviceprovided by another embodiment of the present disclosure; and

FIG. 12 illustrates an interaction system according to the presentdisclosure.

DETAILED DESCRIPTION

To better illustrate the purpose, technical solution and advantages ofthe present disclosure, in a further step, several embodiments of thedisclosure will be detailed described in the below in conjunction withthe accompanying drawings. It is should be understood that the object ofthe embodiments described herein is only to explain the presentdisclosure, not to limit the present disclosure.

In the embodiment, a client scanning a target two-dimensional code,acquiring URL of the target two-dimensional code, sending the URL to anassociated third-party server and receiving multifunction interactioninformation returned from the third-party server according to the URL,and then the client interacts with the third-party server in accordancewith the multifunction interaction information.

The implementation of the present disclosure will be described in detailin connection with the following specific embodiments.

The First Embodiment

FIG. 1 shows a flow chart of an implementation of an interaction methodprovided by the first embodiment of the present disclosure, and thisinteraction method is applied to the client side, the detaileddescription is as follows:

In step S101, a client scanning a target two-dimensional code andacquiring Uniform Resource Locator (URL) of the target two-dimensionalcode;

In this embodiment, the client may be a software unit installed on aterminal device, for example, the client may be QQ client, WeChat clientor software dedicated for two-dimensional code scanning, etc. And theterminal device may be an intelligent terminal, such as iPhone, androidand so on, or other Mobile Internet Devices (MID) and other mobileintelligent terminals, etc.

In this embodiment, the URL actually contained in the two-dimensionalcode is scanned by a scanning device. The URL is an entrance to interactwith the third-party server; the entrance may direct to an interactioninterface to be interacted, or may also get to the interaction interfacethrough several jumps. Actually, as the two-dimensional code is carriedon a printed medium, or other similar medium, it cannot be modifiedsince published. In order to ensure availability of the two-dimensionalcode, preferably, there may exist one or more jumps before getting tothe interaction interface.

In step S102, the client sending the URL to an associated third-partyserver;

In the present embodiment, the third-party server corresponds to aserver of a subscriber, and each URL is associated with a third-partyserver.

In step S103, the client receiving multifunction interaction informationreturned from the third-party server according to the URL, wherein eachpiece of the multifunction interaction information includes interactiontype information and other related information;

In the present embodiment, the interaction applications may beclassified as three categories:

the first category of interaction applications are system applicationslocal to the present client; the second category of interactionapplications are applications developed by the same developer as theclient; and the third category of interaction applications are otherwebpage applications or APP applications developed by a third-party.

In the present embodiment, there may include one or more interactiontypes, for example, the interaction application may be voiceinteraction, SMS interaction, opening a webpage with login state,opening an local APP application of the client, etc. The relatedinformation of the interaction application may be information necessaryfor the interaction application to conduct the interaction operations.Different applications correspond to different contents of relatedinformation, for example, the contents may include an interactionapplication identifier (APPID), an authorized scope of the application,a signature file of a third-party, etc.

In step S104, the client interacts with the third-party server based onthe multifunction interaction information.

In the present embodiment, based on the multifunction interactioninformation, the client may interact with the third-party server in manyforms, for example, sending a message by QQ, sending a short message,making a phone call, opening a specified application, opening a webpagewith login state, etc.

In the present embodiment, a client scans a target two-dimensional codeand acquires a URL of the target two-dimensional code; the client sendsthe URL to an associated third-party server; the client receivesmultifunction interaction information returned from the third-partyserver according to the URL, wherein each piece of the multifunctioninteraction information includes interaction type information; and thenthe client interacts with the third-party server based on themultifunction interaction information. The present method makes itpossible that: during scanning a two-dimensional code, a client candirectly interact with a third-party server, the interactionapplications can simply be acquired via scanning, instead ofpre-scanning and manually initiating an interaction with the scannedcontents, such that the operations are simple and convenient.

The Second Embodiment

Alternatively, after step S130 of the first embodiment, the method mayfurther comprise: displaying options for selecting one type ofinteraction by a user when the multifunction interaction informationincludes multiple pieces each corresponding to one type of interaction;

At this moment, step S104 is specified as: the client interacts with thethird-party server based on the piece of multifunction interactioninformation corresponding to the type of interaction selected by theuser.

Alternatively, after step S101, the method further comprises: Predefinedmultifunction interaction identifier is added into the URL at theclient, wherein this parameter is used to inform the third-party serverthat the current client supports multifunction operation;

At this time, step S102 is specified as: the client sends the URL withadded predefined multifunction interaction identifier to the third-partyserver; and when the third-party server supports multifunctionoperation, the client may receive the multifunction interactioninformation returned from the third-party server according to the URL.

FIG. 2 shows a flow chart of an implementation of an interaction methodprovided by the second embodiment of the present disclosure, thedetailed description is as follows:

In step S201, a client scans a target two-dimensional code and acquiresa URL of the target two-dimensional code;

In step S202, the client adds predefined multifunction interactionidentifier into the URL, wherein the predefined multifunctioninteraction identifier used to inform the third-party server that thecurrent client supports multifunction operation;

In the present embodiment, in order to keep the compatibility of thetwo-dimensional code, a predefined multifunction interaction identifiermay be added into the scanned URL, to inform the third-party server thatthe client supports multiple interaction operations, for example, theURL acquired by scanning ishttp://www.cctv.com/spring2013.html?key1=value1, and the URL after theaddition of the predefined multifunction interaction identifier ishttp://www.cctv.com/spring2013.html?key1=value1&format=rich.

In step S203, the client sends the URL with the added predefinedmultifunction interaction identifier to the third-party server. When thethird-party server supports multifunction operation, step S204 isexecuted.

In the present embodiment, when the third-party server supportsmultifunction operation, the third-party server can interact with theclient normally, step S204 is executed; when the third-party server doesnot support multifunction operation, the third-party server cannotinteract with the client normally, so at this moment, the third-partyserver sends an error message to the client.

In step S204, the client receives multifunction interaction informationreturned from the third-party server according to the URL, wherein eachpiece of the multifunction interaction information includes interactiontype information;

In step S205, when the multifunction interaction information includesmultiple pieces each corresponding to one type of interaction, optionsfor selecting one type of interaction by a user are displayed;

In the present embodiment, the indication may be a menu indication, alist indication, of course, may also be a voice indication or ananimation indication, etc.

In the present embodiment, in order to make interaction more effective,multiple types of interaction applications may be provided in themultifunction interaction information, so that the client may select away of interaction as desired. When the client detects that the receivedmultifunction interaction information includes multiple pieces eachcorresponding to one type of interaction, it will display options forselecting one type of interaction to the user and the user may select adesired type of interaction in the options displayed by the client, andthen step S206 is executed.

In step S206, the client interacts with the third-party server based onthe piece of multifunction interaction information corresponding to thetype of interaction selected by the user.

In the present embodiment, a client scans a target two-dimensional codeand acquires a URL of the target two-dimensional code; the client addspredefined multifunction interaction identifier into the URL and sendsthe URL with the added predefined multifunction interaction identifierto a third-party server; when the third-party server supportsmultifunction operation, the client receives multifunction interactioninformation returned by the third-party server according to the URL; theclient interacts with the third-party server based on the multifunctioninteraction information. This method makes it possible that: during theprocess of scanning a two-dimensional code, a client can directlyinteract with a third-party server, the interaction applications cansimply be acquired via scanning, instead of pre-scanning and manuallyinitiating an interaction with the scanned contents, such that theoperations are simple and convenient.

The Third Embodiment

In the first embodiment, when the interaction type information indicateseither a system application local to the client, for example, a call, aSMS, an e-mail, etc., or an application developed by the same developeras the client, for example, when the client application is WeChatdeveloped by Tencent Company, the interaction application may also beQQ, MicroBlog and so on, then step S104 may be specified as:

The client interacts with the indicated type of application locallycalled by the server by locally calling the same type of application.

For better understanding, the present embodiment is illustrated by thefollowing example implementation, but not limited to the exampleimplementation.

In an example implementation of the disclosure, a call process betweenthe third-party server and the client is taken as an example. At themoment, after the URL is scanned, the following multifunctioninteraction data information may be returned:

{ “version”:“v1.0”, //version “type”: “phone_call”, //making a call“phone”:“4008003333” //phone number of a third-party }

The client determines that the value of “type” is “phone_call” and callsthe corresponded local application of the client to call the phonenumber contained in the “phone” field.

In another example implementation of the disclosure, a SMS processbetween the third-party server and the client is taken as an example. Atthe moment, after scanning the URL, the following multifunctioninteraction data information may be returned:

{ “version”:“v1.0” //version “type”:“sms” //sending a short message“phone”:“100966333” //messaging platform number of a merchant }

The client determines that the value of “type” is “sms” and calls thecorresponded local application of the client to interact with the numbercontained in the “phone” field via short messages.

In yet another example implementation of the disclosure, a chat on QQbetween the third-party server and the client is taken as an example. Atthe moment, after scanning the URL, the following multifunctioninteraction data information may be returned:

{ “version”:“v1.0”, //QQ version number “type”:“QQ_WPA”, // a QQtemporary session “QQ”:“400200333” // QQ number of a third party }

The client determines that the value of “type” is “QQ_WPA” and calls alocal QQ chat window of the client to chat with the QQ number containedin the “phone” field.

In the present embodiment, when the interaction type informationindicates a system application local to the client, or an applicationdeveloped by the same developer as the client application, thecorresponded application may be directly called for interaction toacquire the user's login state information.

The Fourth Embodiment

In another situation, when the interaction application in the firstembodiment is a webpage application or an APP application developed by athird-party, based on the multifunction interaction information, theinteraction in step S104 may be specified as:

the client sends a request for opening a jump URL pointing to theindicated application to the third-party server, so that the third-partyserver will acquire the user's login state information from aninterconnection server according to the request and an authorizationtoken;

the client receives and displays jump webpage returned from thethird-party server, which includes the user's login state information;

the client interacts with the third-party server by using the jumpwebpage;

wherein, the third-party server and the client have been pre-registeredon the interconnection server.

In the present embodiment, acquiring the URL of interaction contentsfrom the jump URL, may be specified as: acquiring the jump URL based onthe URL directly acquired by scanning the two-dimensional code, andopening the jump URL to obtain actual communication contents. The jumpURL can be configured in a variety of forms on the server.

Preferably, after acquiring the user's login state information, the jumpwebpage information may be re-configured based on the login stateinformation to provide the user particular interaction contents based onthe user's features.

Referring to FIG. 3, shows a flow chart of an interaction between aclient and a third-party server provided by the fourth embodiment of thedisclosure, wherein the third-party server and the client have beenpre-registered on an interconnection server. The third-party server ispre-registered on the interconnection server so as to acquireregistration information assigned by the interconnection server, such asthe APPID, the APPKey of the APPID, etc., the detailed description is asfollows:

in step S301, a client scans a target two-dimensional code and acquiresa URL of the target two-dimensional code;

in step S302, the client sends the URL to the associated third-partysever;

in step S303, the client receives multifunction interaction informationreturned by the third-party server according to the URL, wherein eachpiece of the multifunction interaction information includes interactiontype information;

Optionally, the interaction information further comprises an APPIDand/or a signature file of third-party. After step S303, there may be anauthentication process a for the third party:

a. the APPID and/or signature file of the third-party are sent from thethird party to the interconnection server, so that the interconnectionserver authenticates the third-party according to the APPID and/orsignature file of the third-party.

Wherein, the interconnection server compares the locally stored APPIDand/or signature file of the third-party with the received APPID and/orsignature file of the third-party which are sent by the client. When theresult of the above comparison is consistent, the third-party servercorresponding to the third-party is identified as a legitimate server.Otherwise, the third-party server would be identified an illegal server.The authentication can guarantee that the third-party server asking toaccess the user information of the client is a legitimate server, so asto ensure the security of information related to the user.

Optionally, after step S303, there may also be a confirmation process bof the authorized access:

b. a prompt for authorization sent by the interconnection server isreceived by the client. The prompt for authorization is used forconfirming whether the user of the client permits the third-party serverto access information of the user stored on the interconnection server.When a confirmation that permits the third-party server to accessinformation of the user stored on the interconnection server isreceived, the client sends an authorization confirmation to theinterconnection server.

By outputting the prompt for authorization to the user, the user candetermine whether to share the personal information with the third-partyserver as required. Only the information confirmed by the user can beaccessed by the third-party server, which further ensures the securityof user's data.

Optionally, after step S303, there may also be an authorization codesending process c:

c. the client sends the authorization code to the third-party server, sothat the third-party server acquires an authorization token based on theauthorization code; the authorization token can be used to acquire theuser's login state information directly.

Wherein, c may be specified as:

c1. the client receives the authorization code sent from theinterconnection server and forwards the authorization code to thethird-party server; or

c2. the client generates the authorization code locally, and sends theauthorization code to the third-party server.

Optionally, after step S303, there may also be a token sending processd:

d. The interconnection server sends the authorization token to thethird-party server.

Wherein, process d may be specified as:

the interconnection server locally generates the authorization token andsends the authorization token to the third-party server.

By utilizing the above authorization code and authorization token,security of the user's data can be further guaranteed.

It should be noted that the processes a, b, c and d are optionalprocesses, and the execution order of these processes may be set in anyform to satisfy the purpose of the disclosure, instead of limited totheir numerical order.

In step S304, the client sends a request for opening a jump URL pointingto the indicated application to the third-party server, so that thethird-party server acquires the client user's login state informationfrom an interconnection server according to the request and anauthorization token.

In the present embodiment, the login state information is the user'spersonal information, which may include the user's nickname, avatar andso on.

In step S305, the client receives and displays jump webpage informationreturned from the third-party server, which includes the user's loginstate information.

In the present embodiment, when the client has obtained the jump webpageinformation including the user's login state information, the client maycall a local browser to open the jump webpage. At this moment, the userof the client may view the jump webpage containing the user's loginstate information.

In step S306, the client interacts with the third-party server by usingthe jump webpage;

For better understanding, the present embodiment may be described by,but not limited to the following specific example implementation.

In an example implementation of the disclosure, the client opening awebpage of the third-party server is taken as an example to illustratethe interaction process of the present embodiment. Referring to FIG. 4,wherein, the third-party server and the client have been pre-registeredon the interconnection server, here, assuming that the client is aninstant communication client, such as a QQ client and a WeChat client,and that the third-party server may be a merchant server. The detailedprocess is as follows:

1. An instant communication client scans a target two-dimensional codeand acquires a URL of the target two-dimensional code;

2. The instant communication client adds predefined multifunctioninteraction identifier into the URL;

The predefined multifunction interaction identifier is used to informthe third-party server that the present instant communication clientsupports multifunction operation, for example, “format=rich” in thewebpage http://www.cctv.com/spring2013.html?key1=value1&format=rich isthe predefined multifunction interaction identifier.

3. The instant communication client sends the URL with the addedpredefined multifunction interaction identifier to the third-partyserver.

When the third-party server supports multifunction operation, step 4will be executed, in particular, upon the third-party server reads theparameter “format=rich”, step 4 will be executed.

4. The third-party server sends multifunction interaction information tothe instant communication client according to the URL;

Wherein, each piece of the multifunction interaction informationincludes interaction type information, for example, the type of theapplication may be an APPID, and related information of the interactionapplication may include parameters such as an authorized scope of theapplication and the redirect_URL of the jump webpage, and themultifunction interaction information is signed by the APPKey of theAPPID; the interaction information may be data of Json format:

{  “version”:“v1.0”, //version number  “type”:“web”, // represent toopen the webpage to interact  “appid”:“123456”, //interactionapplication identifier  “scope”:“all”, //authorized scope, all means toauthorize the accessing to all the information “redirect_url”:http://www.cctv.com/redirect.php?event=201301234 //address information of an interaction page }.

5. If the multifunction interaction information includes multiple pieceseach corresponding to one type of interaction, the instant communicationclient may display options for selecting one type of interaction to theuser.

6. Based on the piece of multifunction interaction informationcorresponding to the type of interaction selected by the user, theinstant communication client sends the APPID and/or signature file ofthe third-party to the interconnection server. The multifunctioninteraction information includes the APPID and/or signature file of thethird-party.

7. The interconnection server authenticates the third-party according tothe APPID and signature file of the third-party.

Wherein, the interaction information further includes the APPID and/orsignature file of the third-party.

8. When the third-party passes the identity authentication, theinterconnection server sends a prompt for authorization to the instantcommunication client;

The prompt for authorization is used for confirming whether the user ofthe client permits the third-party server to access information of theuser stored on the interconnection server.

When a confirmation that permits the third-party server to accessinformation of the user stored on the interconnection server isreceived, step 9 will be executed.

9. The instant communication client sends an authorization confirmationto the interconnection server.

In the present embodiment, the process of authorizing the access of thethird-party server will be described in the following, but not limitedto this detailed implementation. Certainly, other ways of implementationmay also be applied, for example, the authorization token may bedirectly acquired without an authorization code.

10. The interconnection server sends an authorization code to theinstant communication client.

11. The instant communication client sends a request for opening a jumpURL pointing to the indicated application and the authorization code tothe third-party server.

In the present embodiment, during sending the request, simultaneously,sending the authorization code to the third-party server.

12. The third-party server sends the authorization code to theinterconnection server;

13. Based on the authorization code, the interconnection server sends auser identifier and an authorization token to the third-party server;

14. Based on the user identifier and authorization token, thethird-party server locally sets the instant communication client user'slogin state;

15. The third-party server sends a request for acquiring the login stateinformation to the interconnection server;

16. The interconnection server sends the instant communication clientuser's login state information to the third-party server;

17. The third-party server sends information of the jump webpage, whichincludes the instant communication client user's login stateinformation, to the instant communication client.

18. According to the jump webpage information, the instant communicationclient interacts with the third-party server.

At this moment, the instant communication client may acquire the webpageinformation with login state.

In another example implementation of the disclosure, an interactionprocess between an instant communication client and a merchant (themerchant corresponding to the third-party server) through an APPapplication developed by the merchant is taken as an example. At thismoment, after scanning the URL, following multifunction interaction datainformation may be returned: the type of the application (e.g., APPID)and the related information of the interaction application, which mayincludes parameters such as, a name of the application, an authorizedscope of the application and the redirect_URL. The interactioninformation may be Json format data:

{  “version”:“v1.0”,// version number  “type”:“app”, // representing theAPP to be interacted  “appid”:“123456”,// interaction applicationidentifier  “scope”:“all”,// an authorized scope “redirect_url”:“http://www.cctv.com/redirect.php?event=201301234” ,//opening the website of the application  “appname”:“CCTV”,// contentsof the application “download_url”:http://appstore.apple.com/34567.html”//downloading theURL }

After acquiring the interaction information, the subsequent process issimilar as other embodiments. When the instant communication clientfinds that the content of “type” is “app”, the instant communicationclient opens an application whose “appname” is “CCTV”; if theapplication is not installed on the terminal device, URL in the“download_url” is opened to download the application.

In the present embodiment, when the interaction type informationindicates an APP application or a webpage application developed by athird-party, the client sends a request for opening the jump URLcorresponding to the interaction application to the third-party server,so that the third-party server acquires the client user's login stateinformation from the interconnection server according to the request andan authorization token. The client receives and displays the jumpwebpage information returned from the third-party server with the clientuse's login state information, and simultaneously, interacts with thethird-party server according to the jump webpage information, so thatthe instant communication client may acquire the application or webpagewith login state information.

The Fifth Embodiment

FIG. 5 shows a flow chart of an implementation of an interaction methodat the third-party side provided by the fifth embodiment of thedisclosure, the detailed description is as follows:

In step S501, a third-party server receives a URL sent from a client;

In step S502, the third-party server sends multifunction interactioninformation to the client according to the URL, wherein each piece ofthe multifunction interaction information includes interaction typeinformation.

In the present embodiment, the multifunction interaction informationincludes information about at least one type of interaction application.

In step S503, the third-party server interacts with the client based onthe multifunction interaction information.

In the present embodiment, a third-party server receives a URL sent froma client; the third-party server sends multifunction interactioninformation to the client according to the URL, wherein each piece ofthe multifunction interaction information includes interaction typeinformation; the third-party server interacts with the client based onthe multifunction interaction information. This method makes it possiblethat: during scanning a two-dimensional code, a client can directlyinteract with a third-party server, the interaction applications cansimply be acquired via scanning, instead of pre-scanning and manuallyinitiating an interaction with the scanned contents, such that theoperations are simple and convenient.

The Sixth Embodiment

On the basis of the fifth embodiment, FIG. 6 shows a flow chart of animplementation of an interaction method provided by the fifth embodimentof the disclosure, the detailed description is as follows:

In step S601, a third-party server receives a URL sent from a client;

In step S602, the third-party server receives the URL with addedpredefined multifunction interaction identifier from a client, whereinthe predefined multifunction interaction identifier is used to informthe third-party server that the current client supports multifunctionoperation. When the third-party server supports multifunction operation,step S603 is executed.

In step S603, the third-party server sends multifunction interactioninformation to the client according to the URL, wherein each piece ofthe multifunction interaction information includes interaction typeinformation;

In the present embodiment, the multifunction interaction informationincludes information about at least one the type of interactionapplication.

In step S604, the third-party server interacts with the client based onthe multifunction interaction information.

In the present embodiment, when the third-party server receives the URLwith added predefined multifunction interaction identifier from aclient, and if the third-party server supports multifunction operation,the multifunction interaction information is sent to the client. Thus,while maintaining the compatibility of the two-dimensional code, it alsoprovides a variety of types and forms for interaction. Additionally,multiple application types may be set, so that the user of the clientmay select the best interaction way from multiple interaction ways.

The Seventh Embodiment

In the fifth embodiment, if the interaction application is either asystem application local to the client, for example, a phone call, aSMS, a mail and so on; or an application developed by the same developeras the client application, for example, when the client is WeChat, theinteraction application may be QQ or MicroBlog, etc. then step S503 isspecified as:

The application in the third-party server corresponding to theinteraction application interacts with the client locally callingapplication corresponding to the interaction application.

The present embodiment is a method claim on the third-party server sidethat corresponds to the third embodiment, so the detailed descriptionmay refer to the example implementations in the third embodiment.

In the present embodiment, when the interaction type informationindicates an local application of the client or an application developedby the same developer as the client, the corresponding application maybe directly called to interact to acquire the user's login stateinformation.

The Eighth Embodiment

When the interaction type information indicates an APP application or awebpage application developed by a third-party, step S503 in the fifthembodiment is specified as:

the third-party server receives a request for opening a jump URLpointing to the indicated application from the client;

the third-party server acquires the client user's login stateinformation from an interconnection server according to the request andan authorization token;

the third-party server sends jump webpage information including theclient user's login state information to the client, so that the clientinteracts with the third-party server by using the jump webpage;

wherein, the third-party server and the client have been pre-registeredon the interconnection server.

FIG. 7 shows a flow chart of an implementation of an interaction methodprovided by the eighth embodiment of the disclosure, the detaileddescription is as follows:

in step S701, a third-party server receives a URL sent from a client;

in step S702, the third-party server sends multifunction interactioninformation to the client according to the URL, wherein each piece ofthe multifunction interaction information includes interaction typeinformation.

Alternatively, after step S702, the method may further comprise step 1:

1. The third-party server acquires an authorization token.

Alternatively, before step 1, the method may further comprise:

2. The third-party server acquires an authorization code sent from theclient and executes step 1 according to the authorization code.

Alternatively, during steps 1 and 2, the process that the third-partyserver acquires an authorization token is specified as:

the third-party server acquires an authorization token sent from theinterconnection server and forwarded by the client; or

the third-party server acquires an authorization token locally generatedby the client; or

the third-party server acquires an authorization token sent from theinterconnection server.

In step S703, the third-party server receives a request for opening ajump URL pointing to the indicated application from the client;

In step S704, the third-party server acquires the client user's loginstate information from an interconnection server according to therequest and an authorization token;

In step S705, the third-party server sends jump webpage informationincluding the client user's login state information to the client, sothat the client interacts with the third-party server by using the jumpwebpage;

wherein, the third-party server and the client have been pre-registeredon the interconnection server.

In the present embodiment, when the interaction type informationindicates an APP application or a webpage application developed by athird-party, the third-party server receives a request for opening ajump URL pointing to the indicated application from the client; thethird-party server acquires the client user's login state informationfrom an interconnection server according to the request and anauthorization token; the third-party server sends jump webpageinformation including the client user's login state information to theclient, so that the client interacts with the third-party server byusing the jump webpage; so that a QQ client for example may acquire theapplication or webpage with the login state information.

The Ninth Embodiment

FIG. 8 is a block diagram of an interaction device provided by the ninthembodiment of the disclosure, and for convenience of description, onlyparts related to the embodiment of the disclosure are shown. The devicemay be a software unit, a hardware unit or a combination of them builtin a client.

The device includes: a URL acquiring unit 81, a URL sending unit 82, aninformation receiving unit 83 and an interaction unit 84.

The URL acquiring unit 81 is configured to scan a target two-dimensionalcode and acquire a URL of the target two-dimensional code at the client;

The URL sending unit 82 is configured to send the URL to an associatedthird-party server at the client;

The information receiving unit 83 is configured to receive multifunctioninteraction information returned from the third-party server accordingto the URL at the client, wherein each piece of the multifunctioninteraction information includes interaction type information;

The interaction unit 84 is configured for an interaction between theclient and the third-party server based on the multifunction interactioninformation.

The interaction device provided by the embodiment of the disclosure maybe utilized in the corresponding method embodiment, i.e., the firstembodiment. For details, please refer to the description of the firstembodiment, which are not discussed here.

The Tenth Embodiment

FIG. 9 is a block diagram of an interaction device provided by the tenthembodiment of the disclosure, and for convenience of description, onlyparts that are relevant to the embodiment of the disclosure are shown.The device may be a software unit, a hardware unit or a combination ofthem built in a client.

The device includes: a URL acquiring unit 91, a URL modifying unit 92, aURL sending unit 93, an information receiving unit 94, a indication unit95, an authentication unit 96, an authorization unit 97, anauthorization code sending unit 98, a token sending unit 99 and aninteraction unit 910.

The present embodiment differs from the ninth embodiment in that:

Alternatively, the URL modifying unit 92 is configured to add predefinedmultifunction interaction identifier into the URL at the client, whereinthe predefined multifunction interaction identifier is configured toinform the third-party server that the current client supports themultifunction operation;

The URL sending unit 93 is configured to send the URL with the addedpredefined multifunction interaction identifier to the third-partyserver at the client; and when the third-party server supportsmultifunction operation, the information receiving unit 94 is triggered.

Alternatively, the indication unit 95 is configured to display optionsfor selecting one type of interaction to the user, when themultifunction interaction information includes multiple pieces eachcorresponding to one type of interaction;

The interaction unit 910 is configured for an interaction between theclient and the third-party server based on the piece of multifunctioninteraction information corresponding to the type of interactionselected by the user.

Alternatively, when the interaction type information indicates a systemapplication local to the client or an application developed by the samedeveloper as the client, the interaction unit 910 is further configuredto interact with the indicated type of application locally called by theserver by the client locally calling the same type of application.

Alternatively, when the interaction type information indicates a systemapplication local to the client or an application developed by the samedeveloper as the client, the interaction unit 910 particularlycomprises:

A request sending module 9101, is configured to send a request foropening a jump URL pointing to the indicated application to thethird-party server at the client, so that the third-party server mayacquire the client user's login state information from aninterconnection server based on the request and an authorization token,wherein the third-party server and the client have been pre-registeredon the interconnection server

A jump webpage information receiving module 9102, is configured toreceive and display the jump webpage information including the user'slogin state information and returned from the third-party server at theclient;

An interaction module 9103, is configured to interact with thethird-party server according to the jump webpage information at theclient;

Alternatively, the interaction information further includes aninteraction application identifier and/or a signature file of athird-party server. The device further includes:

The authentication unit 96 is configured to send the interactionapplication identifier and/or signature file of the third-party to theinterconnection server at the client, so that the interconnection serverauthenticates the third-party according to the interaction applicationidentifier and/or signature file of the third-party.

Alternatively, the authorization unit 97 is configured to receive aprompt for authorization sent from the interconnection server at theclient, wherein the prompt for authorization is used for confirmingwhether the user of the client permits the third-party server to accessinformation of the user stored on the interconnection server; when aconfirmation that permits the third-party server to access informationof the user stored on the interconnection server is received from theuser, the client sends authorization information to the interconnectionserver.

Alternatively, the authorization code sending unit 98 is configured tosend the authorization code to the third-party server at the client, sothat the third-party server acquires an authorization token according tothe authorization code.

Alternatively, the authorization code sending unit 98 is furtherconfigured to receive the authorization code sent from theinterconnection server and send the authorization code to thethird-party server at the client; or the authorization code sending unit98 is further configured to locally generate the authorization code andsend the authorization code to the third-party server at the client.

Alternatively, the token sending unit 99 is configured to send anauthorization token to the third-party server at the client.

Alternatively, the token sending unit 99 is further configured toreceive the authorization token sent from the interconnection server andsend the authorization token to the third-party server at the client; orthe token sending unit 99 is further configured to locally generate theauthorization token and send the authorization token to the third-partyserver at the client.

The interaction device provided by the embodiment of the disclosure maybe used in the corresponding method embodiments, namely, the second tothe fourth embodiments. For details, please refer to the description ofthe second to the fourth embodiments, which will not be discussed here.

The Eleventh Embodiment

FIG. 10 is a block diagram of an interaction device provided by theeleventh embodiment of the disclosure, and for convenience ofdescription, only parts that are relevant to the embodiment of thedisclosure are shown. The device may be a software unit, a hardware unitor a combination of them built in a third-party server.

The device includes: a URL receiving unit 101, an information sendingunit 102 and an interaction unit 103.

The URL receiving unit 101 is configured to receive a URL sent from aclient at the third-party server;

The information sending unit 102 is configured to send multifunctioninteraction information to the client according to the URL at thethird-party server, wherein each piece of the multifunction interactioninformation includes interaction type information;

The interaction unit 103 is configured to interact with the client basedon the multifunction interaction information at the third-party server.

Alternatively, the multifunction interaction information includesinformation about at least one type of interaction application.

The interaction device provided by the embodiment of the disclosure maybe used in the corresponding method embodiment, namely, the fifthembodiment. For details, please refer to the description of the fifthembodiment, which will not be discussed here.

The Twelfth Embodiment

FIG. 11 is a block diagram of an interaction device provided by thetwelfth embodiment of the disclosure, which is configured for thethird-party device, and for convenience of description, only parts thatis relevant to the embodiment of the disclosure. The device may be asoftware unit, a hardware unit or a combination of them built in athird-party server.

The device includes: a URL receiving unit 111, an information sendingunit 112, an authorization code receiving unit 113, a token acquiringunit 114 and an interaction unit 115.

The present embodiment differs from the eleventh embodiment in that:

Alternatively, the URL receiving unit 111, is particularly used toreceive a URL with added predefined multifunction interaction identifierand sent from the client at the third-party server, wherein thepredefined multifunction interaction identifier is used to inform thethird-party server that the current client supports multifunctionoperation; when the third-party server supports multifunction operation,the information sending unit 112 is triggered.

Alternatively, when the interaction type information indicates a systemapplication local to the client or an application developed by the samedeveloper as the client, the interaction unit 115 is further configuredfor the interaction between the third-party server's application of thesame type as the interaction application with an application of the sametype as the interaction application and locally called by the client.

Alternatively, when the interaction type information indicates an APPapplication or a webpage application developed by a third-party, theinteraction unit 115 includes:

A request receiving module 1151, is configured to receive a request foropening a jump URL pointing to the indicated application at thethird-party server, and wherein the request is sent from the client;

A login information acquiring module 1152, is configured to acquire theclient user's login state information from an interconnection serveraccording to the request and an authorization token at the third-partyserver, wherein the third-party server and the client have beenpre-registered on the interconnection server;

A webpage information sending module 1153, is configured to send jumpwebpage information including the client user's login state informationto the client at the third-party server, so that the client interactswith the third-party server by using the jump webpage.

Alternatively, the token acquiring unit 114 is configured to acquire anauthorization token at the third-party server.

Alternatively, the authorization code receiving unit 113 is configuredto receive an authorization code sent from the client at the third-partyserver, and the token acquiring unit 114 is triggered based on theauthorization code.

Alternatively, the token acquiring unit 114 is further configured by thethird-party server to receive an authorization token sent from theinterconnection server and forwarded by the client; or to receive anauthorization token locally generated and sent by the client; or toreceive an authorization token sent from the interconnection server.

The interaction device provided by the embodiment of the disclosure maybe used in the corresponding method embodiments, namely, the sixth tothe eighth embodiments. For details, please refer to the description ofthe sixth to the eighth embodiments, which will not be discussed here.

Now turning to FIG. 12, an interaction system 120 is shown according tothe present disclosure. The interaction system 120 includes one or moreclient(s) 121, such as a mobile/cellular phone, a desktop computer, alaptop computer, a tablet computer, and the like. The interaction system120 further includes one or more server(s) 122. The one or moreclient(s) 121 may interact with the one or more server(s) 122 vianetwork 123. Though only one client and one server are shown in FIG. 12,those skilled in the art will appreciate that any number of clients andservers may be included in system 120. The network 123 may be any typeof network, e.g., any combination of Internet, intranet, local areanetwork (LAN), wide area network (WAN), wired network, wireless network,etc. The client may transmit information to or receive information fromthe server over the network.

The above interaction system may implement the interaction methoddescribed by the present disclosure. For details, please refer to thecorresponding embodiments, which will not be discussed here.

It should be noted that, each unit described in the above embodiments issimply divided by the functional logic, but not limited to the abovedivisions, as long as the corresponding functions can be realized;additionally, the name of each functional unit is only used fordistinguishing from each other, and not intended to limit the protectionscope of the disclosure.

Additionally, those skilled in the art can understand that all or partof the steps for implementing the methods of the above embodiments canbe performed via the programs to instruct corresponding hardware. Thecorresponding programs can be stored in a computer readable storagemedium, which may include high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid state storage devices.

The above description only shows several preferred implementations ofthe disclosure, and cannot be used to limit the disclosure. Anymodification, equivalent replacement and improvement within the spiritand principle of the disclosure, should be included in the protectionscope of the disclosure.

What is claimed is:
 1. An interaction method, comprising: scanning,implemented by a processor of a client, a target two-dimensional code toacquire a URL in the target two-dimensional code; sending, implementedby the processor of the client, the URL to a third-party server;receiving, implemented by the processor of the client, multifunctioninteraction information that is returned from the third-party serveraccording to the URL, wherein each piece of the multifunctioninteraction information includes interaction type information thatindicating an interaction manner between the client and the third-partyserver; and interacting, implemented by the processor of the client,with the third-party server based on the multifunction interactioninformation, wherein the interaction type information indicates one ormore members of the group consisting of a system application local tothe client, an application developed by the same developer as theclient, a webpage application and APP application developed by a thirdparty, and wherein, when the interaction type information indicates asystem application local to the client or an application developed bythe same developer as the client, the interacting, implemented by theprocessor of the client, with the third-party server based on themultifunction interaction information comprising interacting,implemented by the processor of the client, with the indicated type ofapplication locally called by the server by locally calling the sametype of application.
 2. The method according to claim 1, wherein, aftersaid receiving, implemented by the processor of the client,multifunction interaction information that is returned from thethird-party server according to the URL, the method further comprises:displaying, implemented by the processor of the client, options forselecting one type of interaction by a user when the multifunctioninteraction information includes multiple pieces each corresponding toone type of interaction; wherein the interacting, implemented by theprocessor of the client, with the third-party server based on themultifunction interaction information comprises: interacting,implemented by the processor of the client, with the third-party serverbased on the piece of multifunction interaction informationcorresponding to the type of interaction selected by the user.
 3. Themethod according to claim 1, wherein, after said scanning, implementedby the processor of the client, a target two-dimensional code to acquirea URL in the target two-dimensional code, the method further comprises:adding, implemented by the processor of the client, a predefinedmultifunction interaction identifier into the URL, wherein thepredefined multifunction interaction identifier is configured to informthe third-party server that the client supports multifunction operation;wherein the sending, implemented by the processor of the client, the URLto a third-party server comprises: sending, implemented by the processorof the client, the URL with the added predefined multifunctioninteraction identifier to the third-party server, and the multifunctioninteraction information is returned when the third-party server supportsmultifunction operation.
 4. The method according to claim 1, wherein,when the interaction type information indicates an APP application or awebpage application developed by a third-party, the interacting,implemented by the processor of the client, with the third-party serverbased on the multifunction interaction information comprises: sending,implemented by the processor of the client, to the third-party server arequest for opening a jump URL pointing to the indicated application, sothat the third-party server acquires a login state of the user of theclient from an interconnection server according to the request and anauthorization token; receiving and displaying, implemented by theprocessor of the client, a jump webpage, which contains the login stateof the user of the client, returned from the third-party server; andinteracting, implemented by the processor of the client, with thethird-party server by using the jump webpage; wherein the third-partyserver and client have been pre-registered on the interconnectionserver.
 5. The method according to claim 4, wherein the multifunctioninteraction information further includes an interaction applicationidentifier and/or a signature file of a third-party; after thereceiving, implemented by the processor of the client, multifunctioninteraction information that is returned from the third-party serveraccording to the URL, the method further comprises: sending, implementedby the processor of the client, the interaction application identifierand/or signature file of the third-party to the interconnection server,so that the interconnection server authenticates the third-partyaccording to the interaction application identifier and/or signaturefile of the third-party.
 6. The method according to claim 4, wherein,before the interacting, implemented by the processor of the client, withthe third-party server based on the multifunction interactioninformation, the method further comprises: receiving, implemented by theprocessor of the client, a prompt for authorization sent from theinterconnection server, wherein the prompt is used for confirmingwhether the user of the client permits the third-party server to accessinformation of the user stored on the interconnection server; sending,implemented by the processor of the client, an authorizationconfirmation to the interconnection server when a confirmation thatpermits the third-party server to access information of the user storedon the interconnection server is received.
 7. The method according toclaim 4, wherein, after the receiving, implemented by the processor ofthe client, multifunction interaction information that is returned fromthe third-party server according to the URL, the method comprises:sending, implemented by the processor of the client, an authorizationtoken to the third-party server.
 8. The method according to claim 7,wherein, the sending, implemented by the processor of the client, anauthorization token to the third-party server comprises: receiving,implemented by the processor of the client, the authorization token sentfrom the interconnection server, and sending, implemented by theprocessor of the client, the authorization token to the third-partyserver; or generating locally and sending, implemented by the processorof the client, the authorization token to the third-party server.
 9. Themethod according to claim 7, wherein, before the sending, implemented bythe processor of the client, the authorization token to the third-partyserver, the method further comprises: sending, implemented by theprocessor of the client, an authorization code to the third-partyserver, so that the third-party server acquires the authorization tokenaccording to the authorization code.
 10. The method according to claim9, wherein, the sending, implemented by the processor of the client, anauthorization code to the third-party server comprises: receiving,implemented by the processor of the client, the authorization code sentfrom the interconnection server, and sending, implemented by theprocessor of the client, the authorization code to the third-partyserver; or generating locally and sending, implemented by the processorof the client, the authorization code to the third-party server.
 11. Aninteraction method, comprising: receiving, implemented by a processor ofa third-party server, a URL sent from a client; sending, implemented bythe processor of the third-party server, multifunction interactioninformation to the client according to the URL, wherein each piece ofthe multifunction interaction information includes interaction typeinformation that indicating an interaction manner between the client andthe third-party server; and interacting, implemented by the processor ofthe third-party server, with the client based on the multifunctioninteraction information, wherein the interaction type informationindicates one or more members of the group consisting of a systemapplication local to the client, an application developed by the samedeveloper as the client, a webpage application and an APP applicationdeveloped by a third party, wherein when the interaction typeinformation indicates a system application local to the client or anapplication developed by the same developer as the client, theinteracting, implemented by the processor of the third-party server,with the client based on the multifunction interaction informationcomprising: interacting, implemented by the processor of the third-partyserver, with the indicated type of application locally called by theclient by locally calling the same type of application.
 12. The methodaccording to claim 11, wherein, the receiving, implemented by theprocessor of a third-party server, a URL sent from a client comprises:receiving, implemented by the processor of the third-party server, theURL with added predefined multifunction interaction identifier sent fromthe client, wherein the predefined multifunction interaction identifieris used to inform the third-party server that the client supportsmultifunction operation, and when the third-party server supportsmultifunction operation, the third-party server sends multifunctioninteraction information to the client based on the URL.
 13. The methodaccording to claim 11, wherein when the interaction type informationindicates an APP application or a webpage application developed by athird-party, the interacting, implemented by the processor of thethird-party server, with the client based on the multifunctioninteraction information comprising: receiving, implemented by theprocessor of the third-party server, a request from the client foropening a jump URL pointing to the indicated application; acquiring,implemented by the processor of the third-party server, login state ofthe user of the client from an interconnection server according to therequest and an authorization token; sending, implemented by theprocessor of the third-party server, to the client a jump webpage, whichcontains the login state of the user of the client, so that the clientinteracts with the third-party server by using the jump webpage; whereinthe third-party server and the client have been pre-registered on theinterconnection server.
 14. The method according to claim 13, wherein,after sending, implemented by the processor of the third-party server,multifunction interaction information to the client based on the URL,the method further comprises: acquiring, by the processor of thethird-party server, an authorization token.
 15. The method according toclaim 14, wherein before acquiring, implemented by the processor of thethird-party server, the authorization token, the method furthercomprises: receiving, implemented by the processor of the third-partyserver, the authorization code sent from the client, and acquiring,implemented by the processor of the third-party server, theauthorization token according to the authorization code.
 16. The methodaccording to claim 14, wherein the acquiring, implemented by theprocessor of the third-party server, an authorization token comprises:receiving, implemented by the processor of the third-party server, theauthorization token sent by the interconnection server and thenforwarded by the client; or receiving, implemented by the processor ofthe third-party server, the authorization token locally generated andsent by the client; or receiving, implemented by the processor of thethird-party server, the authorization token sent from theinterconnection server.
 17. A client comprising a processor, theprocessor functions as: a URL acquiring unit, configured to scan atarget two-dimensional code and acquire a URL from the targettwo-dimensional code; a URL sending unit, configured to send the URL toa third-party server; an information receiving unit, configured toreceive multifunction interaction information that is returned from thethird-party server according to the URL, wherein each piece of themultifunction interaction information includes interaction typeinformation that indicating an interaction manner between the client andthe third-party server; and an interaction unit, configured to interactwith the third-party server based on the multifunction interactioninformation, wherein the interaction type information indicates one ormore members of the group consisting of a system application local tothe client, an application developed by the same developer as theclient, a webpage application and an APP application developed by athird party, and wherein the interaction unit is configured to interactwith the third-party server by interacting with the indicated type ofapplication locally called by the server by locally calling the sametype of application when the interaction type information indicates asystem application local to the client or an application developed bythe same developer as the client.
 18. The client according to claim 17,wherein the processor further functions as: an indication unit,configured to display options for selecting one type of interaction by auser when the multifunction interaction information includes multiplepieces each corresponding to one type of interaction; wherein theinteraction unit interacts with the third-party server, based on thepiece of multifunction interaction information corresponding to the typeof interaction selected by the user.